[Snyk] Upgrade core-js-compat from 3.15.2 to 3.16.0 #4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Snyk has created this PR to upgrade core-js-compat from 3.15.2 to 3.16.0. See this package in npm: https://www.npmjs.com/package/core-js-compat See this project in Snyk: https://app.snyk.io/org/maxmood/project/f6a9764e-fffc-44bc-bde0-3310baa88b95?utm_source=github&utm_medium=upgrade-pr
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to upgrade core-js-compat from 3.15.2 to 3.16.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
Release notes
Package name: core-js-compat
-
3.16.0 - 2021-07-30
- Added
- Work with symbols made stricter: some missed before cases of methods that should throw an error on symbols now works as they should
- Handling
- Fixed work of
- Fixed possible exposing of collections elements metadata in some cases, #427
- Fixed crashing of
- Fixed some cases of typed arrays subclassing logic
- Fixed a minor bug related to string conversion in
- Fixed
- Fixed content of some entry points
- Some minor optimizations and refactoring
- Deno:
- Added Deno support (sure, after bundling since Deno does not support CommonJS)
- Allowed
- A bundle for Deno published on deno.land/x/corejs
- Added / updated compat data / mapping:
- Deno 1.0-1.13
- NodeJS up to 16.6
- iOS Safari up to 15.0
- Samsung Internet up to 15.0
- Opera Android up to 64
- Added
-
3.15.2 - 2021-06-29
- Worked around breakage related to
- Added NodeJS 16.4 -> Chrome 91 compat data mapping
from core-js-compat GitHub release notesArrayfind from last proposal moved to the stage 3, July 2021 TC39 meetingArrayfiltering stage 1 proposal:Array.prototype.filterRejectreplacesArray.prototype.filterOut%TypedArray%.prototype.filterRejectreplaces%TypedArray%.prototype.filterOutArraygrouping stage 1 proposal:Array.prototype.groupBy%TypedArray%.prototype.groupBy@@ toPrimitivein some cases ofToPrimitiveinternal logic made stricterRequestwith polyfilledURLSearchParams, #965Object.create(null)on WSH, #966RegExp#execDate.prototype.getYearfeature detectiondenotarget incore-js-compat/core-js-builderObject.hasOwnmarked as supported from V8 9.3 and FF92Date.prototype.getYearmarked as not supported in IE8-summaryoption tocore-js-builder, see more info in theREADME, #910zone.jsloaded beforecore-js, #953Commit messages
Package name: core-js-compat
NullProtoObjectViaIFrame()on WSH zloirock/core-js#966NullProtoObjectViaIFrame()on WSH zloirock/core-js#966 from gnh1201/masterCompare
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs